Description

Add two reusable skills for adding a new EVM network to MetaMask Swaps/Bridge:

• a Core skill for registering the network in @metamask/bridge-controller;
• a Mobile skill for consuming the released controller support and wiring the unified Swaps/Bridge flow.

The workflows cover authoritative chain/token metadata, hex/decimal/CAIP representations, allowlists, default tokens, stablecoin slippage, dependency release coordination, Bridge API readiness, bridgeConfigV2 rollout, testing, and manual verification. The Swaps domain description now includes both EVM and non-EVM network integration.

Reference implementations:

• MetaMask/core#9007
• MetaMask/core#9459
• MetaMask/metamask-mobile#31413
• MetaMask/metamask-mobile#33110

Type of Change

• New skill
• Skill improvement/update
• Bug fix
• Documentation update
• Other (please describe):

Skill Details (if adding a new skill)

Provider Name: MetaMask

Skill Name: add-evm-network-bridge-controller, add-evm-network-mobile

Brief Description: Repeatable Core and Mobile workflows for adding an EVM network to the unified Swaps/Bridge experience.

Checklist

• I have read the CONTRIBUTING.md guidelines
• My skill follows the SKILL_TEMPLATE.md format
• I have tested this skill with an AI agent
• My skill does not contain any secrets, private keys, or sensitive data
• I have added appropriate documentation
• My changes do not break existing skills

Testing

• node --test test/*.test.mjs — 36 tests passed.
• Installed the skills into isolated Core and Mobile targets with tools/install --domain swaps; each target received only its matching repo overlay.
• Verified discovery with node bin/metamask-skills.mjs list --repo ... --domain swaps --json.
• Forward-tested both skills with independent AI-agent tasks, including missing rollout/API metadata and additive Core changes without existing focused tests.
• git diff --check passed.

The standalone quick_validate.py helper could not run because its Python environment lacks PyYAML; repository-native discovery and installer validation passed.

Additional Context

Core support is the hard controller allowlist layer. Mobile launch readiness also requires Bridge API route support and approved bridgeConfigV2 configuration; the Mobile skill distinguishes those launch gaps from code prerequisites.